Serial command protocol encapsulating wire transfer protocol

ABSTRACT

An embodiment provides a method for transferring information utilizing a serial communication command structure over an unreliable or a non-continuous communication channel, including: establishing a serial command structure, wherein the establishing comprises defining a package structure having a predefined format, wherein the serial command structure comprises bounded data; and transmitting, over the unreliable or the non-continuous communication channel, data from a sending entity to a receiving entity utilizing the serial command structure and in the predefined format. Other aspects are described and claimed.

CROSS REFERENCE TO RELATED APPLICATION

This application claims priority to U.S. Provisional patent ApplicationSer. No. 62/968,610, filed on Jan. 31, 2020, and entitled “SERIALCOMMAND PROTOCOL ENCAPSULATING WIRE TRANSFER PROTOCOL,” the contents ofwhich are incorporated by reference herein.

FIELD

This application relates generally to obtaining information over awireless connection, and, more particularly, to sending informationbetween entities over an unreliable and/or non-continuous communicationchannel utilizing a serial communication command structure.

BACKGROUND

Transmitting information between entities is important. The ability totransmit the information utilizing a wireless connection allows for moreflexibility regarding the entities that can communicate and the locationof the entities with respect to each other. In other words, wirelesstransmissions allow for communication between entities that may notalways communicate with each other or entities that need to communicatewith multiple entities. For example, wireless transmissions allow forcommunication between an instrument and a mobile device, where themobile device can communicate with many instruments. By utilizingwireless communication, the mobile device does not have to be physicallywired into each instrument to receive information from the instrument.Different wireless communication techniques have different proximityrequirements between the sending and receiving entities. For example,some wireless communication techniques may require entities to be inclose proximity to each other, whereas other wireless communicationtechniques allow for a greater distance between the entities.Additionally, different wireless communication techniques have differentreliability and security levels and also different power and processingrequirements than other wireless communication techniques. Thus, thewireless communication technique that is chosen for a particularapplication is critical to ensuring the success of the transmission ofinformation within the application.

BRIEF SUMMARY

In summary, one embodiment provides a method for transferringinformation utilizing a serial communication command structure over anunreliable and/or non-continuous communication channel, comprising:establishing a serial command structure, wherein the establishingcomprises defining a package structure having a predefined format,wherein the serial command structure comprises bounded data, the packetsize limiting an amount of data included in a transmission; andtransmitting, over the unreliable or the non-continuous communicationchannel, data from a sending entity to a receiving entity utilizing theserial command structure and in the predefined format.

Another embodiment provides an information handling device fortransferring information utilizing a serial communication commandstructure over an unreliable or a non-continuous communication channel,comprising: a processor; and a memory device that stores instructionsexecutable by the processor to: establish a serial command structure,wherein the establishing comprises defining a package structure having apredefined format, wherein the serial command structure comprisesbounded data; and transmit, over the unreliable or the non-continuouscommunication channel, data from a sending entity to a receiving entityutilizing the serial command structure and in the predefined format.

A further embodiment provides a product for transferring informationutilizing a serial communication command structure over an unreliable ora non-continuous communication channel, comprising: a storage devicethat stores code, the code being executable by a processor andcomprising: code that establishes a serial command structure, whereinthe establishing comprises defining a package structure having apredefined format, wherein the serial command structure comprisesbounded data; and code that transmits, over the unreliable or thenon-continuous communication channel, data from a sending entity to areceiving entity utilizing the serial command structure and in thepredefined format.

The foregoing is a summary and thus may contain simplifications,generalizations, and omissions of detail; consequently, those skilled inthe art will appreciate that the summary is illustrative only and is notintended to be in any way limiting.

For a better understanding of the embodiments, together with other andfurther features and advantages thereof, reference is made to thefollowing description, taken in conjunction with the accompanyingdrawings. The scope of the invention will be pointed out in the appendedclaims.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example flow diagram for transferring informationutilizing a serial communication command structure over an unreliableand/or a non-continuous communication channel.

FIG. 2 illustrates an example of computer circuitry.

DETAILED DESCRIPTION

It will be readily understood that the components of the embodiments, asgenerally described and illustrated in the figures herein, may bearranged and designed in a wide variety of different configurations inaddition to the described example embodiments. Thus, the following moredetailed description of the example embodiments, as represented in thefigures, is not intended to limit the scope of the embodiments, asclaimed, but is merely representative of example embodiments.

Reference throughout this specification to “one embodiment” or “anembodiment” (or the like) means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, appearances of the phrases “in oneembodiment” or “in an embodiment” or the like in various placesthroughout this specification are not necessarily all referring to thesame embodiment.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided to give athorough understanding of embodiments. One skilled in the relevant artwill recognize, however, that the various embodiments can be practicedwithout one or more of the specific details, or with other methods,components, materials, et cetera. In other instances, well-knownstructures, materials, or operations are not shown or described indetail. The following description is intended only by way of example,and simply illustrates certain example embodiments.

Communication of information between entities is useful for learninginformation from different entities. For example, a sending entity maybe unable to process the information locally and, therefore, must sendthe information to a receiving entity for processing. As anotherexample, a receiving entity may not have the capability to access a widearea network and may, therefore, require an intermediate device toreceive needed data, for example, system updates, firmware updates, andthe like. As another example, other entities may require informationfrom a sending entity in order to analyze the information againstinformation received from other sources or entities. Some entities maynot be connected to a wide area network in order to ensure the securityof the entity. However, these entities still need the ability tocommunicate and receive information. Thus, in order to allowtransmission of information from or to the entity, the entity may beoutfitted with the capability to communicate with other entitieswirelessly. To ensure that these communications remain secure, thechosen wireless communication technique may only allow transmission ofthe information a short distance, for example, utilizing a near fieldcommunication technique, a short range communication technique, or thelike.

Additionally, since the entity may be battery powered, the chosenwireless communication technique needs to require little power.Traditionally, these types of wireless communication techniques arenon-continuous communication channels, meaning they do not continuouslytransmit information and, instead, only transmit information when thereis information to be transmitted. By being non-continuous, thesewireless communication techniques require substantially less power,thereby preserving battery power. One drawback to such communicationtechniques is that the amount of information that can be transmittedover the channel is usually very small with very small data packets.This is because the traditional way of utilizing these communicationtechniques is to transfer small packets of information. Thus, if asending entity needs to transfer data that is larger than allowed by thecommunication technique, there is conventionally no mechanism ortechnique for doing so. Accordingly, more robust data transmissiontechniques must be utilized.

Accordingly, an embodiment provides a system and method for transferringinformation utilizing a serial communication command structure over anunreliable and/or a non-continuous communication channel. The system andmethod utilizes a serial communication command structure structure thatdefines a package structure. By defining a serial communication commandstructure structure, the system can emulate serial-type communication,or continuous stream communication, over an unreliable and/or anon-continuous communication channel. The package structure identifies apredefined format for data transmission within the serial communicationprocess. Placing data to be transmitted in the predefined format of theserial command structure, the data can be transmitted over an unreliableand/or a non-continuous communication channel from a sending entity to areceiving entity. The receiving entity can then process and verify thedata, and take any action with respect to the data as needed by thereceiving entity.

The illustrated example embodiments will be best understood by referenceto the figures. The following description is intended only by way ofexample, and simply illustrates certain example embodiments.

Referring to FIG. 1 , an example system and method for transferringinformation utilizing a serial communication command structure over anunreliable and/or a non-continuous communication channel is illustrated.The non-continuous communication channel may be any connection thatallows serial communication, for example, a short-range communicationchannel such as BLUETOOTH Low Energy (also called BLUETOOTH Smart),Wi-Fi, or the like. BLUETOOTH is a registered trademark of BluetoothSIG, Inc., in the United States and other countries. The unreliableand/or non-continuous communication channel may be a communicationchannel that only transmits information when triggered, usually whenthere is information to be transmitted. Thus, an unreliable and/or anon-continuous communication channel is not continuously broadcastinginformation and only broadcasts information when the sending entity hasinformation to broadcast. This type of communication channel requiresless power as compared to continuous communication channels, therebyextending the battery life of the sending entity.

An example that will be used throughout this application, one of thesending or receiving entities is an instrument that takes measurementvalues, for example, water quality measurement values. The role of theinstrument can change between the sending entity and the receivingentity depending on whether data is being transmitted to or from theinstrument. For example, in the scenario that the instrument istransmitting measurement values, the instrument would be the sendingentity. On the other hand, in the scenario that the instrument isreceiving a firmware update, the instrument would be the receivingentity. The other entity may be a portable device, for example, a mobilephone, a tablet, a laptop, an instrument reader, or the like. Theportable device may include an application that can both send data toone or more instruments and receive data from one or more instruments.

At 101, the system establishes a serial command structure. The serialcommand structure is a serial structure that can be utilized withserial-type communication channels, for example, those mentioned above.However, since the above mentioned communication channels are notdesigned for sustained data transfer and communication, the serialcommand structure is designed to allow for more data, meaning largerdata packets, to be transmitted across the unreliable and/ornon-continuous communication channel. In other words, a serial commandstructure is established that allows for a reliable data stream thatallows for larger data packet transmissions than is conventionallyallowed across the unreliable and/or non-continuous communicationchannel. For example, system updates can be transmitted from a portabledevice to an instrument. By establishing a serial command structure, thesystem can ensure that data can be sent over an unreliable and/or anon-continuous communication channel even if the protocol for sendingthe data is in a continuous stream. In other words, even if the data issent in a continuous stream due to the format of the serial commandstructure, the unreliable and/or non-continuous communication channelcan identify a start and an end to a data packet and ensure the entiretyof the data packet is transmitted, thereby providing reliable datatransmission.

The serial command structure defines a package structure having apredefined format. The predefined format may include a marker, command,or other identifier that identifies the start of a packet. Thepredefined format may also include a marker, command, or otheridentifier that identified the end of a packet. Knowing the start andend of the packet allows the receiving entity to be able to determine ifthe entire packet was received. Accordingly, the end command may be theoutput of an algorithm that validates all of the data was sent and thatit was not changed during transmission. Also included in the predefinedformat may be the location of data within the packet. This data maycorrespond to the data that is being transmitted. Other information maybe included within the data packet, for example, how much data is in thepacket, a timestamp associated with transmission of the data, or thelike. Accordingly, the predefined format may identify the location ofthis information within the data packet.

The serial command structure is established between all entities (e.g.,receiving entities, sending entities, applications, systems, etc.) thatmay be using the command structure. In other words, the format definedby the serial command structure is known to any of the devices, systems,or applications that will be sending, receiving, or otherwisemanipulating information that is formatted per the serial commandstructure. In order to maintain security of information transmittedutilizing the serial command structure, the serial command structure mayinclude encryption. In this case, the serial command structureidentifies how information will be encrypted so that it can be decryptedby a system, device, or application that is also utilizing the serialcommand structure, upon receipt of the information. Utilizing encryptionmay include just encrypting or obfuscating the data within the datapacket or may include encrypting or obfuscating the entire data packet.

Additionally, the serial command structure defines a predetermined datapacket size, which can be a default data packet size or a data packetsize defined by a user, system, or application. The predetermined datapacket size is also referred to as bounded data. The data packet sizelimits an amount of data that can be included in a transmission. Thepredetermined data packet size, although not specifically required, isgenerally larger than a data packet size that would be conventionallytransmitted utilizing the selected communication channel. In the casethat data to be transmitted is larger than the data packet size, thesystem may chunk the data into packet sizes that correspond to the datapacket size. For example, if an instrument needs to receive a systemupdate that is 3 kB, but the instrument can only receive 1 kB datatransmissions, the system can chunk the data into three chunks of 1 kB.If, additionally, the communication channel only allows datatransmissions of 256 B, the system chunks each of the 1 kB chunks intosmaller chunks to fit within the communication channel size limits.

At 102, the system prepares to transmit the data. Any type of data canbe prepared and placed within the data packet. Preparing the data withinthe data packet may include serializing the information into byte data,evaluating the size of the data, and using an algorithm to generate avalue for future validation of the data. Preparation may also includeidentifying bytes that are reserved for the serial command structuredefinition and replacing those bytes with a marker and modified bytepair.

Per the example used here throughout, the information may include, butis not limited to, instrument identifiers or other identificationinformation, measurement data obtained by the instrument, timestampinformation which may identify when the data packet wascreated/transmitted or may identify when the measurement data wasobtained, parameters of the instruments or devices of the instrument(e.g., probes, sensors, meters, lamps, etc.), a combination thereof, orthe like. Measurement data may include any data that the instrument isdesigned to capture, for example, pH values of a water source, turbidityvalues of a fluid, lamp intensity output, specific indicator (e.g.,chlorine, fluoride, iron, etc.) values, or any other measurement data.Parameters of the instruments may include information identifying whatis being measured by the instrument, ranges or scales of the measurementdata, measurement data unit information, information identifying what isbeing measured by each device of the instrument, and the like. The typeof information that may be included in the data packet can be any typeof information and may vary across different instruments, receivingentities, or sending entities.

At 103, the system encapsulates the data by assembling the serialcommand packet. This may include placing the data and metadata in apredetermined order. For instance, the packet may be predefined to havea command byte, followed by bytes representing the size of the data,followed by the data itself, and then finally including the validationvalue generated by an algorithm. The entire packet may then have startand stop bytes added to the beginning and end, respectively.

At 104, the system transmits or sends the data, over the unreliableand/or non-continuous communication channel, from the sending entity tothe receiving entity. The transmission includes transmitting the data inthe predefined format and utilizing the serial command structure. Thedata can be read by a receiving entity as long as the data conforms tothe predefined format of the serial command structure.

Transmission of the data may be triggered via one of a plurality ofmechanisms. One trigger may include the receiving entity requesting datafrom a sending entity. Another trigger may include the sending entitynotifying the receiving entity that it has data to transmit andtransmitting the data in response to receiving a response from thereceiving entity. Another trigger may include the sending entity havinginformation to transmit and simply broadcasting or publishing theinformation without determining whether a receiving entity is inproximity or will receive the information. In this scenario, a receivingentity may subscribe to the sending entity. Then, whenever the sendingentity broadcasts or publishes information, the receiving entity simplyreceives the information without requiring additional steps.

Different triggers allow for different levels of interaction between thereceiving and sending entities. Utilizing the trigger where thereceiving entity requests information requires the entities to have adirect interaction and communicate with each other before thetransmission of data. On the other hand, using the broadcasting trigger,the entities do not have to have a direct interaction or communicatewith each other before receiving the information. Thus, the selectedtrigger may be based upon a level of interaction that a facility,system, or application wants to require between the two entities.Different interaction levels may result in different security levels.For example, if the receiving entity has to request the information, thereceiving entity may have to provide some security token or identifierto the sending entity before the sending entity will make a connectionand transmit information, thereby providing a more secure datatransmission. On the other hand, even broadcast information can besecured through the use of data encryption as discussed above.

At 105, the data is received by the receiving entity, which maydetermine whether the data matches the serial command structure. If not,the receiving entity may use the same predetermined serial commandstructure to send an error message back to the original sending entity,as shown at 106. Upon receiving a packet that does conform to thepredetermined serial command structure, the information will be unpackedand further evaluated for whether it can be understood, as indicated at107 and 108. If it cannot be understood, the receiving entity may usethe same predetermined serial command structure to send an error messageback to the original sending entity, again as shown at 106.

At 109, upon receiving properly formatted data that can be understood,the receiving entity may provide a verification transmission back to thesending entity indicating that the data was received and could be read.In the example where the data was chunked into different chunks, afterreceiving the verification transmission from the receiving entity, thesending entity may send the next chunk of data. Thus, each of the datachunks may be transmitted separately, but the system can be assured thateach data chunk was received and readable. This allows for large chunksof data to be sent while ensuring that the transmission is reliable.This is particularly useful when the data to be sent is something thatcould cause a change with the receiving entity, and, data receivedincorrectly, would result in malfunctions, for example, a system orfirmware update, addition of an application, setting changes, or thelike.

In the publish/subscribe example, determining if the data can be read bythe receiving entity may simply be performed by the receiving entity.Unless the receiving entity is unable to read the information, thesending entity may continue to publish or broadcast information. In theevent that it cannot be read, the receiving entity may notify thesending entity of the misread. The sending entity may then resend thedata. Other methods for determining if the data can be read arecontemplated and possible. For example, if the sending entity does notreceive a verification transmission at all or within a predeterminedtimeframe after sending the data, the system may assume that the datawas not readable or received by the receiving entity. As anotherexample, if the receiving entity indicates that the data was damaged,the system may identify the data as unreadable. Other verificationtechniques are possible.

If the receiving entity has received data that can be understood, thesystem may take an action at 110. The action that is taken may bedependent on the receiving entity and the data that was transmitted. Forexample, if the transmitted data was a system update and was received byan instrument, the instrument may execute the system update. As anotherexample, if the transmitted data was measurement data and was receivedby an application on a portable device, the application may display themeasurement data, for example, in a graphical user interface within theapplication. Additionally, the application may analyze the measurementdata and/or send the measurement data to a central server or centraldata storage location for processing, analysis, and/or storage.

It should also be noted that if the data was encrypted, the action mayinclude decrypting the data in order to read the data. Additionally,reading the data includes reading the data packet in view of the serialcommand structure. In other words, the receiving entity is able tounderstand the data packet because the system can decipher the datapacket, particularly the data packet format, based upon knowing thepredefined format of the serial command structure.

The various embodiments described herein thus represent a technicalimprovement to conventional techniques for transmission of informationutilizing an unreliable and/or a non-continuous communication channel.The described system and method allows for transmission of data that islarger than typically allowed within the communication channel. In otherwords, using the serial command structure allows for transmission oflarge amounts of data within data packets having a predefined format,thereby allowing for reliable communication of the data. Accordingly,the sending entities can conserve battery power using an unreliableand/or a non-continuous communication channel and still receive largeamounts of data that would normally require different types ofcommunication channels. Additionally, the serial command structureallows for encryption of the data, thereby providing a secure, reliabletechnique for transmitting data between sending and receiving entities.

While various other circuits, circuitry or components may be utilized ininformation handling devices, with regard to an instrument for totalchlorine measurement in seawater according to any one of the variousembodiments described herein, an example is illustrated in FIG. 2 .Device circuitry 10′ may include a measurement system on a chip designfound, for example, a particular computing platform (e.g., mobilecomputing, desktop computing, etc.) Software and processor(s) arecombined in a single chip 11′. Processors comprise internal arithmeticunits, registers, cache memory, busses, I/O ports, etc., as is wellknown in the art. Internal busses and the like depend on differentvendors, but essentially all the peripheral devices (12′) may attach toa single chip 11′. The circuitry 10′ combines the processor, memorycontrol, and I/O controller hub all into a single chip 11′. Also,systems 10′ of this type do not typically use SATA or PCI or LPC. Commoninterfaces, for example, include SDIO and I2C.

There are power management chip(s) 13′, e.g., a battery management unit,BMU, which manage power as supplied, for example, via a rechargeablebattery 14′, which may be recharged by a connection to a power source(not shown). In at least one design, a single chip, such as 11′, is usedto supply BIOS like functionality and DRAM memory.

System 10′ typically includes one or more of a WWAN transceiver 15′ anda WLAN transceiver 16′ for connecting to various networks, such astelecommunications networks and wireless Internet devices, e.g., accesspoints. Additionally, devices 12′ are commonly included, e.g., atransmit and receive antenna, oscillators, PLLs, etc. System 10′includes input/output devices 17′ for data input and display/rendering(e.g., a computing location located away from the single beam systemthat is easily accessible by a user). System 10′ also typically includesvarious memory devices, for example flash memory 18′ and SDRAM 19′.

It can be appreciated from the foregoing that electronic components ofone or more systems or devices may include, but are not limited to, atleast one processing unit, a memory, and a communication bus orcommunication means that couples various components including the memoryto the processing unit(s). A system or device may include or have accessto a variety of device readable media. System memory may include devicereadable storage media in the form of volatile and/or nonvolatile memorysuch as read only memory (ROM) and/or random access memory (RAM). By wayof example, and not limitation, system memory may also include anoperating system, application programs, other program modules, andprogram data. The disclosed system may be used in an embodiment toperform total chlorine measurement of a sample of seawater.

As will be appreciated by one skilled in the art, various aspects may beembodied as a system, method or device program product. Accordingly,aspects may take the form of an entirely hardware embodiment or anembodiment including software that may all generally be referred toherein as a “circuit,” “module” or “system.” Furthermore, aspects maytake the form of a device program product embodied in one or more devicereadable medium(s) having device readable program code embodiedtherewith.

It should be noted that the various functions described herein may beimplemented using instructions stored on a device readable storagemedium such as a non-signal storage device, where the instructions areexecuted by a processor. In the context of this document, a storagedevice is not a signal and “non-transitory” includes all media exceptsignal media.

Program code for carrying out operations may be written in anycombination of one or more programming languages. The program code mayexecute entirely on a single device, partly on a single device, as astand-alone software package, partly on single device and partly onanother device, or entirely on the other device. In some cases, thedevices may be connected through any type of connection or network,including a local area network (LAN) or a wide area network (WAN),personal area connection (PAN), or the connection may be made throughother devices (for example, through the Internet using an InternetService Provider), through wireless connections, e.g., near-fieldcommunication, or through a hard wire connection, such as over a USBconnection.

Example embodiments are described herein with reference to the figures,which illustrate example methods, devices and products according tovarious example embodiments. It will be understood that the actions andfunctionality may be implemented at least in part by programinstructions. These program instructions may be provided to a processorof a device, e.g., a hand held measurement device, or other programmabledata processing device to produce a machine, such that the instructions,which execute via a processor of the device, implement thefunctions/acts specified.

It is noted that the values provided herein are to be construed toinclude equivalent values as indicated by use of the term “about.” Theequivalent values will be evident to those having ordinary skill in theart, but at the least include values obtained by ordinary rounding ofthe last significant digit.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The example embodiments were chosen and described in orderto explain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure for variousembodiments with various modifications as are suited to the particularuse contemplated.

Thus, although illustrative example embodiments have been describedherein with reference to the accompanying figures, it is to beunderstood that this description is not limiting and that various otherchanges and modifications may be affected therein by one skilled in theart without departing from the scope or spirit of the disclosure.

What is claimed is:
 1. A method for transferring information utilizing aserial communication command structure over a wireless unreliable or anon-continuous communication channel, comprising: establishing a serialcommand structure to emulate serial-type communication over the wirelessunreliable or the non-continuous communication channel, wherein theestablishing comprises defining a package structure having a predefinedformat allowing for transmission of large data packet transmissionsacross the wireless unreliable or the non-continuous communicationchannel, wherein the predefined format comprises a start packetidentifier and an end packet identifier and defines a location of datawithin a data packet formatted per the predefined format, wherein theserial command structure comprises bounded data having a predeterminedpacket size; and transmitting, over the wireless unreliable or thenon-continuous communication channel and responsive to receiving atrigger to transmit data, the data from a sending entity to a receivingentity utilizing the serial command structure and in the predefinedformat, wherein the wireless unreliable or the non-continuouscommunication channel comprises a communication channel that is notcontinuously broadcasting information from the sending entity and thattransmits serial communications, wherein the transmitting compriseschunking the data into a plurality of packets based upon the packetsize, wherein each of the plurality of packets comprises a start packetidentifier and an end packet identifier that are added to each of theplurality of packets after placing the data within the each of theplurality of packets.
 2. The method of claim 1, wherein the chunking isresponsive to identifying the data has a size greater than the packetsize and wherein the chunking comprises chunking the data into datachunks having a size no larger than the packet size and wherein thetransmitting comprises transmitting each of the data chunks separately.3. The method of claim 1, wherein the package structure comprises analgorithm that validates the data was sent and that the data was notchanged during the transmitting.
 4. The method of claim 1, wherein thetransmitting comprises publishing the data and wherein the receivingentity subscribes to the publishing to receive the data.
 5. The methodof claim 1, comprising verifying receipt of the data by the receivingentity via receipt of a response transmission from the receiving entityat the sending entity.
 6. The method of claim 5, comprisingretransmitting the data responsive to not receiving a verification ofreceipt of the data by the receiving entity.
 7. The method of claim 1,wherein the data is encrypted within the serial command structure. 8.The method of claim 1, wherein the non-continuous communication channelcomprises a short-range communication channel.
 9. An informationhandling device for transferring information utilizing a serialcommunication command structure over a wireless unreliable or anon-continuous communication channel, comprising: a processor; and amemory device that stores instructions executable by the processor to:establish a serial command structure to emulate serial-typecommunication over the wireless unreliable or the non-continuouscommunication channel, wherein the establishing comprises defining apackage structure having a predefined format allowing for transmissionof large data packet transmissions across the wireless unreliable or thenon-continuous communication channel, wherein the predefined formatcomprises a start packet identifier and an end packet identifier anddefines a location of data within a data packet formatted per thepredefined format, wherein the serial command structure comprisesbounded data having a predetermined packet size; and transmit, over thewireless unreliable or the non-continuous communication channel andresponsive to receiving a trigger to transmit data, the data from asending entity to a receiving entity utilizing the serial commandstructure and in the predefined format, wherein the wireless unreliableor the non-continuous communication channel comprises a communicationchannel that is not continuously broadcasting information from thesending entity and that transmits serial communications, wherein thetransmitting comprises chunking the data into a plurality of packetsbased upon the packet size, wherein each of the plurality of packetscomprises a start packet identifier and an end packet identifier thatare added to each of the plurality of packets after placing the datawithin the each of the plurality of packets.
 10. The informationhandling device of claim 9, wherein the chunking is responsive toidentifying the data has a size greater than the packet size and whereinthe chunking comprises chunking the data into data chunks having a sizeno larger than the packet size and wherein the transmitting comprisestransmitting each of the data chunks separately.
 11. The informationhandling device of claim 9, wherein the package structure comprises analgorithm that validates the data was sent and that the data was notchanged during the transmitting.
 12. The information handling device ofclaim 9, wherein the transmitting comprises publishing the data andwherein the receiving entity subscribes to the publishing to receive thedata.
 13. The information handling device of claim 9, comprisingverifying receipt of the data by the receiving entity via receipt of aresponse transmission from the receiving entity at the sending entity.14. The information handling device of claim 13, comprisingretransmitting the data responsive to not receiving a verification ofreceipt of the data by the receiving entity.
 15. The informationhandling device of claim 9, wherein the data is encrypted within theserial command structure.
 16. A product for transferring informationutilizing a serial communication command structure over a wirelessunreliable or a non-continuous communication channel, comprising: astorage device that stores code, the code being executable by aprocessor and comprising: code that establishes a serial commandstructure to emulate serial-type communication over the wirelessunreliable or the non-continuous communication channel, wherein theestablishing comprises defining a package structure having a predefinedformat allowing for transmission of large data packet transmissionsacross the wireless unreliable or the non-continuous communicationchannel, wherein the predefined format comprises a start packetidentifier and an end packet identifier and defines a location of datawithin a data packet formatted per the predefined format, wherein theserial command structure comprises bounded data having a predeterminedpacket size; and code that transmits, over the wireless unreliable orthe non-continuous communication channel and responsive to receiving atrigger to transmit data, the data from a sending entity to a receivingentity utilizing the serial command structure and in the predefinedformat, wherein the wireless unreliable or the non-continuouscommunication channel comprises a communication channel that is notcontinuously broadcasting information from the sending entity and thattransmits serial communications, wherein the transmitting compriseschunking the data into a plurality of packets based upon the packetsize, wherein each of the plurality of packets comprises a start packetidentifier and an end packet identifier that are added to each of theplurality of packets after placing the data within the each of theplurality of packets.